IBIS Macromodel Task Group Meeting date: 14 Jun 2011 Members (asterisk for those attending): Agilent: * Fangyi Rao * Radek Biernacki Ansoft: Chris Herrick Danil Kirsanov Ansys: Samuel Mertens * Dan Dvorscak Deepak Ramaswamy Jianhua Gu * Curtis Clark Arrow Electronics: Ian Dodd Cadence Design Systems: Terry Jernberg * Ambrish Varma Celsionix: Kellee Crisafulli Cisco Systems: * Mike LaBonte Stephen Scearce Ashwin Vasudevan * Syed Huq Ericsson: Anders Ekholm IBM: Greg Edlund Intel: Michael Mirmak LSI Logic: Wenyi Jin Mentor Graphics: * John Angulo Vladimir Dmitriev-Zdorov Zhen Mu * Arpad Muranyi Micron Technology: Randy Wolff NetLogic Microsystems: Ryan Couts Nokia-Siemens Networks: * Eckhard Lenski Sigrity: Brad Brim Kumar Keshavan Ken Willis SiSoft: * Walter Katz Mike Steinberger * Todd Westerhoff Doug Burns Snowbush IP: Marcus Van Ierssel ST Micro: Syed Sadeghi Teraspeed Consulting Group: Scott McMorrow * Bob Ross TI: Casey Morrison Alfred Chong Vitesse Semiconductor: Eric Sweetman Xilinx: Mustansir Fanaswalla The meeting was lead by Arpad Muranyi ------------------------------------------------------------------------ Opens: - None -------------------------- Call for patent disclosure: - None ------------- Review of ARs: All: Please send comments to Arpad by email on the topic of how Corner typ/slow/fast should be associated with typ/min/max in IBIS - Not done Arpad: Submit AMI Function Return Value Clarification BIRD draft to Open Forum - Done (BIRD 134) Walter: Remove Samples_Per_Bit from BIRD 121 - Done (BIRD 121.1) Walter: Send email from Mike Steinberger to Ambrish answering his question: Are these maximum values for the model? - Not done? Arpad: Send reminder emails to ATM reflector about documents which are planned for vote. - Done Arpad: Update the BNF BIRD draft with Todd's comment: Put "floating point number" before "ANSI ..." - Done Arpad: Update the Out_InOut_BIRD draft to include the words: "in order to be compliant with this specification, Model_Specific parameters ... must not ..." - Done Ambrish: Update the Type_Format_Table_BIRD draft so that Integer should not be allowed - Remove checkmark for DjRj, Gaussian as Integer type - Done ------------- New Discussion: Arpad showed the Type and Format BIRD draft from Ambrish: - Ambrish: There have been four changes from the last version - The BIRD draft was approved by acclamation AR: Ambrish submit Type and Format BIRD draft to open forum Arpad showed the Add Boolean to BNF BIRD draft: - Arpad highlighted some text that will be removed - Radek: This should be done before submission - Mike: It is clear what will be submitted - Radek: That is OK - The BIRD draft was approved with changes by acclamation AR: Arpad submit Add Boolean to BNF BIRD draft to open forum Arpad showed the AMI_parameters_out Clarification BIRD draft: - Arpad: There is a change 3.1.2.7&9 to specify that it affects AMI_Init - Also in 3.2.2.4 it affects AMI_GetWave - Should it say the other function is not to use it? - Walter: That is not necessary - Ambrish: Is it technically possible to do that? - Arpad: One allocates a string and the other could use it - Todd: We see this as a status report from Init - Walter: GetWave is not to return anything this way - Curtis: Agree with Walter - Code should not hang on to memory pointers - It could crash - It may be more confusing to explain this though - Arpad: This will be voted next week - Radek: The sentence "it may ignore" should be removed - It is unnecessary - Arpad: I worked with Curtis on this - There are three options to return nothing - Todd: If you are not returning anything just don't mess with the pointer - Radek: It should just say don't set anything - Arpad: We should have a rule that to return nothing do nothing - Todd: Agree - Arpad: The text will remain unchanged Arpad showed the Corner and Range Clarification BIRD draft: - Arpad: There is no way to associate min/typ/max with /slow/typ/fast - Mike: Tools can always just tell users what they are doing and that is OK - Todd: It says "slow does not have to be less than fast" - That implies numeric comparison, not necessarily the case - It is not needed - Bob: Corners can be a string variables - Arpad: It just says there is no requirement - Mike: It could say no relationship is required - Arpad: Then "relationship" would have to be explained - Radek: It is well defined if the tool allows user selection of fast/slow - Arpad: The model maker may have some prescribed use in mind - Radek: Slow and fast are clear - We do not have to add anything - Todd: The tool is supposed to know which parameters to take - Arpad: We could include how to handle I-V curves here to explain it - Bob: That should not be required - Walter: It is clear how to use AMI parameters - Mike: The AMI model has slow/fast and the EDA tool has slow/fast - Only the IBIS buffer has min/max - Arpad: The B element has 5 corners including min/max - Todd: max I-V is fast, min I-V is slow - Walter: We only need to say that in an AMI file typ/min/max doesn't mean what IBIS 5.0 says it means - Arpad: We should finish this by email - Bob: I like the wording without this BIRD Walter: We should form an editorial committee: - Editorial cleanups have been discussed already - Some clarification BIRDs passed today should go to the committee - Arpad: We should not bypass open forum approval - Some BIRDs have been submitted already - Walter: The rewrite has to be approved anyway - Bob: For AMI the BIRD wordings have not been critical - The base document is disorganized anyway - Arpad: Agree there should be an editorial committee - Bob: The BIRDs should be forum approved - We already have an editorial committee - Documentation standards are being set - Arpad: Isn't it nearly done? - Bob: Not even close - Walter: We should refer this to the editorial committee - We should work on technical issues like Jitter and Analog - Bob: Not all issues are closed - Arpad: The editorial committee can make only editorial changes - Bob: Do not agree with this process - The rewrite effort may discover new changes that are needed - Arpad: We can set aside 5 or 10 minutes for this in the next meeting Meeting ended. ------------- Next meeting: 21 Jun 2011 12:00pm PT Next agenda: 1) Task list item discussions ------------- IBIS Interconnect SPICE Wish List: 1) Simulator directives